home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 11
/
Cream of the Crop 11-2.iso
/
bbs
/
twast23.zip
/
TWASTMAC.DOC
< prev
next >
Wrap
Text File
|
1995-12-02
|
39KB
|
1,140 lines
▄ ▄
▀▀█▀▀ █▀▀▄ █▀▀▀█ █▀▀▄ █▀▀▀ █▄ ▄█ █▀▀▀█ █▀▀▄ █▀▀▀
█ █▄▄▀ █▄▄▄█ █ █ █▀▀ █ ▄█▄ █ █▄▄▄█ █▄▄▀ ▀▀▀█
█ █ █ ▄█ █▄ █▄▄▀ █▄▄▄ █▄█ █▄█ ▄█ █▄ █ █ ▄▄▄█
▄ ▄
███████ ███████ ███████ ██ ███████ ██████ ███████ ██ ██ ██████
██ ██ ██ ██ ██ ██ ██ ██ ██ ███▄ ██ ██
███████ ███████ ███████ ██ ███████ ██ ███████ ██▀██▄██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ▀███ ██
███ ███ ███████ ███████ ██ ███████ ██ ███ ███ ██ ██ ██
▄
█▀█ █▀█ █▀▀▀█ █▀▀█ █▀▀▄ █▀▀█ █▀▀▀
█ ▀█▀ █ █▄▄▄█ █ █▄▄▀ █ █ ▀▀▀█
█▀ ▀█ ▄█ █▄ █▄▄█ █ █ █▄▄█ ▄▄▄█
Version 2.3
for use with
Trade Wars 2002 Assistant
contributed by many
╔════════════════════════════════════════════════════════════════════════════╗
║ Table of Contents ║
╚════════════════════════════════════════════════════════════════════════════╝
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 General Information . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Universe mappers . . . . . . . . . . . . . . . . . . . . . . 4
3 Qmodem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Telix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5 Procomm Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6 Commo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7 Telemate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8 Procomm Plus for Windows . . . . . . . . . . . . . . . . . . . . . 19
Page 2
╔════════════════════════════════════════════════════════════════════════════╗
║ Section 1 Introduction ║
╚════════════════════════════════════════════════════════════════════════════╝
People have contributed these macros to help users capture the reports
during a Trade Wars session. You are not required to use them. You may
capture the information in the manner that best suits you. The macros are
a bonus and are not considered part of the TWASSIST software.
These macros are provided as freeware. You may modify them for your own
use. You may distribute modified macros as a separate package but you may
not distribute modified macros as part of any TWASSIST package.
░▒▓█ 1.1 █▓▒░ Disclaimer
The macros are provided AS IS. Neither Sasquatch Software nor the macro
authors provide any warranty, either expressed or implied, with respect to
the software or documentation, including but not limited to their quality,
performance, merchantability, or fitness for a particular purpose. In no
event will Sasquatch Software or the author be liable for direct, indirect,
special, incidental, or consequential damages arising out of the use,
misuse, or inability to use the software or documentation, even if advised
of the possibility of such damages.
Page 3
╔════════════════════════════════════════════════════════════════════════════╗
║ Section 2 General Information ║
╚════════════════════════════════════════════════════════════════════════════╝
The section title is the name of the communications program the macro is
for. Each section will include the name of the macro file, the author of
the macro, and information on how to use the macro. All of the macros are
in the TWASTMAC.ZIP file. Find the macro file you want to use, as named in
the section for your communications program, and extract it from the file.
Typically the macros were developed to be executed from the main Trade
Wars menu. Each section will identify any special requirements.
WARNING: These macros will invoke computer interrogation mode in the game
and do a port report. There is a bug in v1.03 of Trade Wars 2002
where it will kick you out of the game if you have not ported or
statused a port before doing this. To prevent this, either port
or get a port status from the computer. You can do this with
any port except a class 0.
░▒▓█ 2.1 █▓▒░ Universe mappers
The macros have a feature to map the structure of the TW universe using
route commands prepared by TWASSIST. They run TWASSIST to prepare the file
of route commands to be sent to the CIM prompt in the game. The macro
reads the route commands from the file and sends them to the game while
pacing with the game's prompts and capturing the data from the game. It
then runs TWASSIST to read the capture file and prepare another list of
route commands. Repeat the sequence to gather more data on the warps in
the universe. If you don't have enough time to get all the data at once
do it a little each day. See the section on Map universe routes in the
TWASSIST doc for more information.
The universe mapper macros should run smoothly and continuously but they
are very dependent on text and prompts from the game to properly pace the
inputs to the game. If the macro does not see the text it is looking for
or gets something unexpected (e.g. line noise, unanticipated situations,
changes to text by TW2002 v2.0, etc.) it may hang. If that happens then
take a guess at what the response to the games prompt should be and enter
it yourself. The macro may be able to pick it up from there.
The most troublesome part of creating a macro for the universe mapper
is turning off ANSI in the game. Different versions of the game have
different ways of changing the ANSI status. It is not required to have
ANSI off for the mapper to work but it does improve performance. The ANSI
data about doubles the amount of data in a route transferred over the modem
eventhough you don't see it yourself. With high speed modems the time for
the game to calculate the routes and for running TWASSIST are a bigger
factor. Still ANSI can increase the overall time by 25%. For low speed
modems the data transfer becomes a more important factor. At 2400 baud it
takes about twice as long to map the universe. With ANSI on that time can
be increased about 50% over running with ANSI off. If you have problems
with the ANSI section of the macro try commenting that portion of the macro
out. You can manually turn ANSI off prior to running the mapper to get the
better performance.
Page 4
╔════════════════════════════════════════════════════════════════════════════╗
║ Section 3 Qmodem ║
╚════════════════════════════════════════════════════════════════════════════╝
File: TWASSIST.SCR
By: Albin Gersich
Date: 11/24/95
Gathering all the data that TWASSIST can use is as simple as pressing a
key with this script. You can use it as is or customize it for your own
use. There are a few variables at the top of the script that may need to
be modified for your configuration.
This script provides a menu of options, allowing you to capture all the
reports used by TWASSIST or just some of them. Maybe you don't have much
time left and you only want to get the CIM reports, or you have just started
your session and want to get updates on fighter and mine deployment. Here
is the menu:
(T)W2002 Assistant
(A)ll reports
(C)IM sector and port reports
(P)ort report
(F)ighters, mines, and avoids
(M)ap universe routes
E(x)it script
Your selection?
The option that runs TWASSIST has two variables that may need changing
depending on where files are located on your system. One variable specifies
the location of the TWASSIST executable, the default is c:\tw\twassist.exe.
The other variable is the directory where your data files are stored, the
default is c:\tw. This directory variable is used to change your current
directory to that location before running TWASSIST allowing you to enter
your database name without the full path.
Example key assignment (CTRL-F10 for example):
- Press ALT-J in QModem
- Press '3' to assign a CTRL key
- Move cursor to key field (example: CTRL-F10 field)
- Type @SCRIPT TWASSIST
- Press F10 to save
- Press ESC to exit
QModem Usage:
- Start your screen capture by pressing CTRL-HOME
- Make sure you are at the main command prompt in Trade Wars.
- Execute the TWASSIST.SCR file by pressing the key assigned to it.
- Select the macro option from the menu shown.
- When your screen stops you can press CTRL-HOME to close the screen
capture.
Page 5
╔════════════════════════════════════════════════════════════════════════════╗
║ Section 4 Telix ║
╚════════════════════════════════════════════════════════════════════════════╝
File: TWASSIST.SLT
File: TWA_MAP.SLT
By: Phil Crown
Date: 07/17/94 v1.4
Gathering all the data that TWASSIST can use is as simple as pressing a
key with this script. I've included the source code for those who want to
incorporate this into their own scripts, or you can customize this one.
You must compile the script as described in the note below before you can
use them.
The scripts have been updated to support Trade Wars 2002 v2 wide beta
games. They should be able to handle v1.03(d) games was well.
This script provides the following menu of options, allowing you to
capture all the reports used by TWASSIST or just some of them. Maybe you
don't have much time left and you just want the CIM reports, or you have
just started your session and want to get updates on deployed fighters
and mines.
╒═ 02/05/93 - D. Roseen - v1.3 ═╕
│ │
│ (T)W2002 Assistant │
│ │
│ (A)ll reports │
│ (C)IM warp and port reports │
│ (P)ort report │
│ (F)ighters, mines, and avoids │
│ (M)apping the universe │
│ │
│ E(x)it script │
│ │
│ Your selection? │
│ │
╘═══════════════════════════════╛
*** NOTE! *** If your TWASSIST directory is not C:\TW you you MUST
change the default TWASSIST directory in the Telix script source code for
proper operation! This is the directory which contains your TW Assistant
executable and data files. You can change it with a simple ASCII text
editor and recompile the source code by running Telix's CS.EXE program
(e.g. CS TWASSIST) and CS.EXE will create a new TWASSIST.SLC file from your
revised TWASSIST.SLT file. The directory variable is used to change your
current directory to that location before running TWASSIST. This makes it
easier to enter the name of the database at the TWASSIST prompt. You only
have to enter the name instead of the full path.
Page 6
4 Telix (cont'd)
Example key assignment (CTRL-F10 for example):
- Press ALT-K in Telix
- Select default of "Regular" or press 'R'
- Select "Edit" or press 'E'
- Press the key you want it assigned to (example: CTRL-F10)
- Type @TWASSIST
- Press the space bar since you don't want to assign any more keys.
- Select "Save" or press 'S' and save to a key file.
- Select "Exit" or press 'E'
Telix Usage:
- Start your screen capture by pressing ALT-L
- Make sure you are at the main command prompt in Trade Wars.
- Execute the TWASSIST.SLC file by pressing the key assigned to it. You
will see the menu and then make your selection.
- When your screen stops you can press ALT-L and close the screen capture.
Update: The update from 1.2 to 1.3 was done by Stephen Whitis, in
preparation for the release of TWAssist 2.0. The TWAssist script runs
exactly as it did before, with one exception. There is now a menu
selection for (M)apping the universe. When the user chooses that
command, the TWASISST.SLC script will call another script named
TWA_MAP.SLC. That is the script which handles mapping by acting as the
messenger between TWASSIST and the TW2002 cim mode.
TWA_MAP can also be called directly, by adding a call to it via your key
file, just as you did with TWASSIST.SLC.
The remainder of these notes apply to TWA_MAP.SLT and .SLC.
** Note ** These notes only apply if you are using TWA_MAP.SLT in a v1.03x
game.
If your TWASSIST directory is not C:\TW you you MUST change the default
TWASSIST directory in the Telix script source code for proper operation!
This is done by modifying and compiling TWA_MAP.SLT the same way you did
with TWASSIST.SLT, documented above.
TWA_MAP must be run from the "Command [TL" prompt. It will not run
unless you begin at that point.
When TWA_MAP runs, it will ask for a gamename. This is the name of the
database TWASSIST is using for your current game. You can enter a
leading path if needed, but if you don't, it will use the current
directory. (And if you have defined the default directory in TWA_MAP,
you shouldn't need to enter a leading path at all.)
Page 7
4 Telix (cont'd)
TWA_MAP will check to see if a file named <gamename>.DAT exists. If it
does, TWA_MAP continues. If not, TWA_MAP generates a warning. If you
should already have a TWASSIST database for this game, you can abort. If
you don't, you can continue, and one will be created.
The next prompt will ask for how many warps to plot. The default is 250
for 2400 baud modems, 400 for faster modems, and 100 for slower modems.
Any number from 100-1000 is valid.
After that prompt, everything is automated. After the warps have been
plotted and processed, you will be asked if you wish to continue. If you
do, it will plot the same number of warps again (using different paths,
of course.)
When TWA_MAP runs, it will turn ANSI off, and save the original ANSI
status to restore when it finishes. It will also close your capture
file, if you have one open, and save information so it can re-open the
capture file if needed. The capture file which TWA_MAP uses will be
deleted after each call to TWAssist, and will not use your default
filename.
Page 8
╔════════════════════════════════════════════════════════════════════════════╗
║ Section 5 Procomm Plus ║
╚════════════════════════════════════════════════════════════════════════════╝
File: ASTV2B.ASP 08/27/94
File: PTRADE1.ASP 05/17/94
File: SHADOW1.ASP 03/21/93
By: Rick Cooney
Date: (noted above)
ProComm Plus 2.01 script for use with TWAssist
----------------------------------------------
(thrown together by Rick Cooney)
First off, I almost didn't submit these scripts to Albin cause I
really, really hate writting documentation. So, if any of what follows
is unclear....
Second, by running these scripts you accept full responsibility for
anything that occurs, either real or imagined, that is related to
running them in even the slightest way.
It's assumed that you are familiar with the way PCPlus uses script
files so no attempt will be made to explain them. Read your manual
if your not up to speed.
I always ran the script from my PCPlus directory since the directory
is setup to be accessable from any drive or directory.
My TWAssist files were kept in a seperate directory named assist.
-------------------------------
All scripts run most efficiently with ansi off. Some have a tendency
to hang with ansi on.
All filenames that are prompted for should be entered _without_ an
extension. I didn't included any code to trap names entered with an
extension. If you include one the script will more than likely return
an error.
-------------------------------
What do the scripts do?
The main script is modeled after the PCPlus scripts written by Jason
Jiggins that were distributed with TWAssist ver. 1.0. They have been
updated to work with both TW2002 versions 103/d and 2.0 beta. An inter-
face to the Zero Turn mapping function in TWAssist was added using the
Telemate and QModem scripts (written by Stephen Whitis and Albin Gersich)
as a guide.
Page 9
5 Procomm Plus (cont'd)
The purpose is to ease the gathering of data used by TWAssist. The
script interfaces with TW2002 to create port, sector, fighter, mine,
and avoid reports either all in one or in seperate files.
An option to run TWAssist from a shell to dos is included but it's
success is dependent on the availibility of the memory required by
TWAssist.
The "map universe routes option" interfaces with TWAssist zero turn
mapping function.
The script is menu driven and self explanatory. You will be prompted
for any information you need to provide.
-------------------------------
Setup
Copy the files astv2b.asp and shadow1.asp to your PCPlus Directory or
where ever you wish to run them from. It's up to you to decide how they
will be run. I have them included in a tradewar.key file that I load when
I am playing TW.
You must alter the astv2b.asp script to point to the directory that
your TWAssist files are kept in. The following is the scetion of the
script that must be changed. Load the script into an editor (pcedit.exe
works well) and find the following section.
; -----------------------IMPORTANT-----------------------
define DataDir "d:\assist" ; change this to the path to your TW Assist files.
; To avoid having to add the path to every file
; used the script first changes to this dir.
; --------------------------------------------------------
Replace the "d:\assist" with your own TWAssist directory.
Just as a warning, the mapping funtion writes a temporary file named
capture.txt to the TWAssist directory when it is run. Any file in the
directory with the same name will be deleted. If that's a problem you'll
have to search astv2b.asp for "capture.txt" and name it something else.
-------------------------------
Did any of that make sense?
Page 10
5 Procomm Plus (cont'd)
No? I can be reached in the Fido Tradewars echo or by netmail at
1:2613/133. Maybe if you ask a specific question I can give a clear
answer.
I've been using these scripts in various forms for a couple of years.
They work for me. If they don't work for you, tell me what's happening.
Maybe I can point you in the right direction.
-------------------------------
Just for laughs I included a paired port trading script. If the others
meet your needs, give this one a try.
It needs to be run from the main TW command line while at one of a
matched pair of ports. You'll need a psychic probe and turn ansi off.
It's not on the menu. You'll have to set up a seperate meta key to run it.
Page 11
╔════════════════════════════════════════════════════════════════════════════╗
║ Section 6 Commo ║
╚════════════════════════════════════════════════════════════════════════════╝
File: TWASSIST.MAC
By: Mark Cothran
Date: 11/20/93
This Macro can only be used from COMMO v5.4. It added a menu system to
the programming languange and will NOT work with earlier versions. I wrote
this using v5.5, but did not include any of the fancy new menuing commands
that goes with newer versions.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
WHY:
Often all you need is just a few updates to your database, not a full
update, although you sometimes want that too!
HISTORY:
Three note worthy events: Fred Brucker releases Commo 5.4, Fred Polli
releses Power Macros for Commo and Albin Gersich releses TW Assistant,
...from then own, your competition is history!
INSTALLATION:
You will need to decide WHICH key to put this macro on. This will depend
on what macros you already use. At Present, Power Macros (v1.9,v2.5 and,v3)
does not use Shift F1 key, so you may use that, or the ALT-V as suggested
in an earlier macro..the choice is yours!
1) Move the TWASSIST.MAC file to the area where the rest of your Commo
Macro's are.
2) From the Main Terminal Menu, hit ALT-G. You will need to add the
following line to your configuration file:
{set twasst,C:\terminals\commo\assist}
╙─────────┬─────────────╜
│
└──< or whereever YOUR Assist directory is!
~~~~
This is also a good time to make sure your "_hom" variable is set.
Thats the directory to the Commo root directory. Using the example
above, it would be "{setv _hom,C:\terminals\commo}"
Completelly exit Commo (ALT-X), and re-boot it for the new config
to take effect.
Page 12
6 Commo (cont'd)
3) From the main terminal prompt, hit ALT-M to call up the macro processor
menu you will need to ADD (EDIT) the following line to your macro:
╓────╥───< IF you want the SHIFT F1 Key (see COMMO.DOC)
║ ║
{:sf1}{macl-r twassist.mac,twassist}{}
4) Power Macro Users - See the note below
Enter the terminals dialer menu and somewhere add another variable
called the "pref" variable. This is a name assigned to the variable
PREF that will allow you to keep the data files seperate for different
games automatically. I've seen a wide variance in dialer screens for
Commo, but a generic one is like this:
NAME: Last Called: Number: Password: Variable:
Night Owl BBS 11/19/93 {12066314949} {****} {pref,nightowl}
It doesn't matter where you put it, as long as it's a unique name for
each BBS and is in the format {pref,BBSNAME}.
Now, by pressing SHIFT F1 from the terminal, it will load up TWASSIST.MAC
and give you a menu to do things from. Please consult MACRO.DOC (Commo)
for more information about changing the ALT-KEY combinations that
execute the macro.
As long as you don't have any other macro's assigned the SHIFT F1 key,
you can use that.
5) To return to your normal macros, hit the F10 Key!!!
POWER MACROS NOTE:
Since the Version 3.0 PWRMAC's that I wrote this from uses 5 seperate
macros (commo.mac, powermac.mac, other.mac, other1.mac, and user.mac) you
will need to add line 3 to *ALL* the macros to ensure that you can move from
one area to another without a problem. Use the Commo editor (ALT-U) and edit
each macro. (ADD line 3 above to ALL your macros.)
If your already using PREF variables, then you can skip step 4 above.
**** If you aren't using Power Macros, just add the line to COMMO.MAC. ****
CONCLUSION:
At present, I can be contacted via the RIME Tradewars echoes (which I
moderate), and occasionally on the FIDO and WWIV Tradewars Conferences.
Or you can reply to Albin and he can get us together.
Page 13
6 Commo (cont'd)
USE TIPS:
1. The macro MUST be ran from the Main Screen in Tradewars.
2. I added an option to delete OLD GAME.DAT files, read the prompts!
3. The NEW mapping routines from TWASSIST v2: This was the real reason
for an update to the macro. The macro reads a text file generated
from TWASSIST, opens a capture, then interrogates the remote game.
If you encounter problems, make sure your twassist variable is included
in with COMMO.SET file. (See # 2 above!)
4. If after editing it in and you DON'T get a menu, then re-do # 3 above!
5. As Albin expands the auto-command language, there may be more updates.
6. As a default, I have the max routes plotted set to 250. If you decide
that you want to permantently change the number, then edit the macro
and change the "maxro" variable to what you want. You do have an option
to temporarilly change them while online as well.
USER LICENSE:
Support the Shareware Authors efforts, register THEIR products! This is
released to the public as freeware, all I ask you do do is register your
verion of TWASSIST.
Feel free to hack and rip into the macro as you see fit.
Page 14
╔════════════════════════════════════════════════════════════════════════════╗
║ Section 7 Telemate ║
╚════════════════════════════════════════════════════════════════════════════╝
File: TWASSIST.TLM (source code)
(NOTE: The file was originally named TWASSIST.SCR. This caused a
conflict with the name already used by the Qmodem script.
I renamed the file to TWASSIST.TLM to put in the archive.
You should rename it back to TWASSIST.SCR after you retrieve
it from the archive.
-- Albin)
File: TWASSIST.TMS (compiled code)
By: Francis Ng
Date: 03/28/95
* denotes new information for the 03/28/95 update
This script makes gathering the various reports that TWAssist can use
easy. Just turn on a capture file, run the script, and make a menu
selection. In addition, the script will act as the interface between the
new TWASSIST mapping routines and Telemate, allowing you to learn about
most of the warps in a universe without using a turn.
* These scripts have been updated to work properly with the
the v2 betas. v1.03 is no longer supported. Changes include:
-The ability to run TWASSIST from a directory other than
Telemate.
-Gathering of both limpet and normal mines reports.
-The scripts will now keep track of what TWASSIST data file
prefixes you use depending on what BBS you are connected to
and automatically pass the data file prefixes on to TWASSIST.
This information is stored in a file called TWTM.BBS
which will created in your Telemate directory.
-When capturing reports, the scripts will automatically
create a log file called CAPTURE.TXT in your TWASSIST directory.
INSTALLATION
Before you can use the script, you need to put everything in place. If
you have a script directory for Telemate, put this script there. If not,
Telemate will look in the same directory as telemate itself. I like
having a seperate directory for scripts, but it isn't necessary. You
also need TOOLBOX1.SCR and TOOLBOX2.SCR available in that same directory.
These come with Telemate. The TWASSIST.SCR file has a #include line for
each of these which includes a path name. You will need to edit that
path name to make sure it points to the right directory.
* You will also need to enter a directory path to your
TWAssist executables. Please see TWASSIST.TLM.
If you haven't already done so, you must define your
Telemate directory in the TM directory setup. It can be
reached by pressing Alt-O then I from the menu bar.
Page 15
7 Telemate (cont'd)
Telemate also comes with a program called TMS.EXE. It compiles scripts,
such as TWASSIST.SCR into the codes that Telemate uses. The first time
you try to run TWASSIST.SCR Telemate will use TMS.EXE to compile the
script, creating TWASSIST.TMS.
The "Map the Universe" part of the script will call TWAssist as it runs.
I am not a Telemate user. I wrote these to help out TW players who use
Telemate because Albin had mentioned that many people had asked for
scripts to support Telemate such as the ones available for Telix and
other comm programs. Since I'm not a Telemate user and learned the
script language just for this script, there are probably improvements
that can be made. If you make any improvements, please consider sending
them to Albin, so he can consider distributing them with future versions
of TWAssist.
With everything in place as described, you can start the script by
pressing Alt-S and selecting TWASSIST.SCR (or TWASSIST.TMS once it's been
created.) But an easier way would be to create a macro tied to a key so
that a single key-press would start the script. To do this, first run
Telemate. In Telemate, press Alt-M. That will pop up a macro screen.
Pressing Alt-M again will give you a menu. You can tie the script to
whichever key you want - I'll give directions for Alt-F1. On the
macro-menu, one of the choices is A)lt keys. Press A, and a box will
appear showing what the macros for the various Alt keys are. Select the
Alt-F1 line. Enter "^\TWASSIST.SCR" (with no quotes). Save the changes
and exit out. Now pressing Alt-F1 should run the script.
USING THE SCRIPT
When you run the script (after pressing Alt-S and selecting it, or after
using your hot-key) you will get a menu which looks similar to this.
╔══════════════════════════════╗
║ ║
║ (T)W2002 Assistant ║
║ ║
║ (A)ll reports ║
║ ║
║ (C)IM warp and port reports ║
║ (P)ort report ║
║ (F)ighters, mines and avoids ║
║ ║
║ (M)ap the Universe ║
║ ║
║ (E)xit script ║
║ ║
║ Your Selection? ║
║ ║
╚══════════════════════════════╝
Page 16
7 Telemate (cont'd)
You can run TWAssist, gather reports (either all, or just some, depending
on your need,) or do mapping. Just make a selection.
Most of the choices don't need much explanation.
* If you choose to capture reports, the scripts will open a capture
file called "CAPTURE.TXT" in the TWAssist directory. ANSI will
be turned off when gathering reports or mapping - and it will be
restored after the scripts have run depending on if ANSI was on
or not before the script was started. By default, the scripts
will turn off the Animation setting inside TW.
I will explain the Mapping choice a bit though.
When you use mapping script, it will be turning a capture file on and
off, and deleting the file from time to time. If a capture file is open
when you start mapping, that file will be closed. It will not be opened
again when the script ends.
When you choose mapping, the script will ask you for a filename. Don't
give an extension. The filename is the name you use for that game in
TWAssist. For example, I did my testing on Reynard's Keep BBS. I used
the name REYNARDS for it. If I was playing on The Chess Board BBS, I
might use CHESSBRD.
* The mapping procedure will use a TWTM.BBS entry if it is
available.
If you have not used TWAssist with that filename, the .DAT file won't
exist. In that case the script will warn you, and ask if you want to
continue. If you mistyped the filename, say no. If this is the correct
filename, and you haven't run TWAssist for that game yet, say Yes to
continue.
The script will also ask how many warps to plot. It will give a default,
which is recommended. The default varies with your baud-rate.
After the script has done one group of warps, you will be asked if you
want to continue. The amount of time left should affect your choice.
* ADDITIONAL INFORMATION
The following applies only if you have connected to a BBS
using Telemate's dialing directory.
The scripts will store TWAssist data file prefixes
along with their corresonding Telemate BBS Dialing Directory
Entries in a file (TWTM.BBS) which will automatically be
created the first time you try to run TWAssist from the
script menu.
Page 17
7 Telemate (cont'd)
If no TWAssist data file entry is found in TWTM.BBS, you will
be prompted to enter one. This data file entry should be relative
to your TWAssist directory. If you just enter a name
(such as hawknest), the corresponding TWAssist data files
will be located in your TWAssist directory. You may also
enter directories. If you wish to store all your Hawk's Nest
TWAssist data files in a directory called hawknest, you can
enter hawknest\hawknest. Note that in order to use a
directory, the directory must exist prior to you running
the script (ie. the hawknet\ directory must already exist).
After entering the new database file you will be asked if you
would like the database file written to TWTM.BBS. You would
normally chose yes.
If you have not connected using the TM dialing directory,
each time you run TWAssist from the script menu, you will have
to manually enter the data file name.
Page 18
╔════════════════════════════════════════════════════════════════════════════╗
║ Section 8 Procomm Plus for Windows ║
╚════════════════════════════════════════════════════════════════════════════╝
File: TWCAP.WAS
File: TWMAP.WAS
By: Neil Catone
Date: 08/22/94 v1.20 Updated for Trade Wars 2002 v2 beta
(Neil did not submit anything for this doc. I am extracting a few things
from the comments in the files and looked for some special places to be
noted. I suggest you read through the comments in the files before using
them. -- Albin)
These scripts were developed with Procomm Plus for Windows. The scripts
were written and tested with ProComm Plus for Windows v1.01.
To compile the scripts (make them useable), edit them the way you want,
(the comments that begin with a ';' are okay to leave in -- they don't
affect the file in any way) copy them into your \PROWIN\ASPECT\ directory,
and COMPILE AND RUN. The scripts may be assigned to a Meta-key for ease
of use.
From TWCAP.WAS:
ATTENTION! This file will get your deployed fighters, deployed mines,
the game status (V), your avoids and also gets you into the C.I.M. to
get your port & warp info. It will automaticaly log all of this to the
C:\PROWIN\TW\ directory as the file 'TW.CAP', then return the default
capture path to C:\PROWIN\CAPTURE\. You may need to change this
information to reflect your directory configuration.
NOTE that this script will delete your last 'TW.CAP' if it exists to
keep your data files from getting overgrown.
(I noticed one place in TWCAP.WAS where you need to edit in a sector number
that has a port. -- Albin)
From TWMAP.WAS:
ATTENTION! This file will get route info from the Trade Wars
computer C.I.M. mode. It will automaticaly log all of this to the
C:\PROWIN\TW\ directory as the file 'MAP.CAP', then return the default
capture path to C:\PROWIN\CAPTURE\. You may need to change this
information to reflect your directory configuration.
NOTE that this script will delete your last 'MAP.CAP' if it exists to
keep your data files from getting overgrown.
Prior to running this macro, you must create the "game.CIM" file
from TWASSIST. Under the <R>oute Reports menu, select <M>ap universe
routes and follow the instructions. The more the route commands, the
longer it will take online, depending on baud rate. Reference
TWASSIST.DOC for more information on mapping universe routes.
Page 19
